[v0.36.0] release prep: bump k8s/go deps, manifests, docs, and CI matrix by a7i · Pull Request #1874 · kubernetes-sigs/descheduler

a7i · 2026-05-16T02:18:36Z

This PR prepares descheduler for the v0.36.0 release by combining dependency/toolchain updates with release-facing docs and manifest alignment in one change set.

What changed

Bumped Kubernetes dependency stack to 1.36 line and updated related Go modules.
Updated Go toolchain/runtime settings to 1.26 and aligned build/test scripts.
Updated CI manifest workflow matrix to target:
- Kubernetes v1.36.1
- descheduler v0.36.0
- kind v0.35.1
Updated release manifests to use descheduler image v0.36.0:
- Deployment
- Job
- CronJob
Updated release-facing documentation for v0.36:
- Added v0.36 docs branch mapping
- Added v0.36 compatibility matrix entry
- Added v0.36 container image entry in user guide
Included generated/API updates related to new eviction-per-namespace policy typing and conversion/deepcopy updates.

Why

This follows the same release-prep pattern used in:

[v0.35.0] bump to kubernetes 1.35 deps #1827 (deps + toolchain + upstream compatibility updates)
[v0.35.0] update docs and manifests #1832 (docs/manifests/workflow release version alignment)

and keeps all release-cut prep in one PR for easier review and traceability.

Validation

Verified YAML/doc edits are structurally clean in editor checks.
Local tree is internally consistent for release versions across workflow, manifests, and docs.

Suggested reviewer focus

Dependency/toolchain bump impact and generated file diffs.
API type/conversion changes around namespace eviction limits.
Release version consistency across CI, manifests, and docs.

Release impact

No behavioral feature additions intended.
Primary impact is version alignment and release readiness for v0.36.0.

Copilot

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

Copilot

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

Copilot

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

Copilot

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

a7i · 2026-05-17T13:13:14Z

/retest-required

Copilot

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

Copilot

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

a7i · 2026-05-17T19:02:22Z

/cc @jklaw90 @ingvagabund

jklaw90 · 2026-05-17T19:38:43Z

/lgtm

ingvagabund · 2026-05-18T15:42:34Z

e2e_evictioninbackground_test.go:320: Expected at least 3 finished live migrations, got less: 0

There might be something in it. Maybe the kubevirt version needs to be bumped?

https://github.com/kubevirt/kubevirt/releases/tag/v1.7.3 ?

a7i · 2026-05-18T15:53:46Z

Let me do that and also rebase the PR

ingvagabund · 2026-05-18T19:36:30Z

Compared to previous successful TestLiveMigrationInBackground runs the background eviction of the VM pods never started. The logs show the same initial pods:

42776 e2e_evictioninbackground_test.go:268] vmi pods: []string{"virt-launcher-kubevirtvmi-1-w2htl", "virt-launcher-kubevirtvmi-2-qf5tv", "virt-launcher-kubevirtvmi-3-bbklr"}

All three pods should be eventually replaced with new ones.

The current e2e do not dump the sufficient logs to see why the eviction in background did not start. Better to debug this locally.

EDIT: correction. There are some errors in the "virt-handler" controller logs. Maybe that has the answer.

- Update kubevirt.io/api from v1.3.0 to v1.8.2 - Update kubevirt.io/client-go from v1.3.0 to v1.8.2 - Update kubevirt.io/containerized-data-importer-api from v1.57.0-alpha1 to v1.64.0 - Migrate e2e test from deprecated generated clientset path (kubevirt.io/client-go/generated/kubevirt/clientset/versioned) to new kubevirt.io/client-go/kubevirt client package - Update vendor and dependencies for Kubernetes 1.36 compatibility

Copilot

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

ingvagabund · 2026-05-19T09:29:21Z

Comparing logs of a successful run (1.35) and a failed run within the virt-handler container (the current PR) and a locally reproduced (the current PR) there's the following error pattern:

{"component":"virt-handler","kind":"","level":"info","msg":"containerdisk containerdisk not yet ready","name":"kubevirtvmi-1","namespace":"default","pos":"mount.go:401","reason":"container disk socket path not found for vmi                                                         
  \"kubevirtvmi-1\"","timestamp":"2026-05-19T08:00:26.247839Z","uid":"3c8d6d7d-a852-460f-bd61-20d84a8ea42b"}
...
{"component":"virt-handler","controller":"vm","kind":"","level":"info","msg":"migration is block migration because of containerdisk                                                                                                                                                     
  volume","name":"kubevirtvmi-1","namespace":"default","pos":"vm.go:1820","timestamp":"2026-05-19T08:00:26.287236Z","uid":"3c8d6d7d-a852-460f-bd61-20d84a8ea42b"}                                                                                                                       
  {"component":"virt-handler","controller":"vm","kind":"","level":"info","msg":"migration is block migration because of cloudinitdisk                                                                                                                                                     
  volume","name":"kubevirtvmi-1","namespace":"default","pos":"vm.go:1820","timestamp":"2026-05-19T08:00:26.287287Z","uid":"3c8d6d7d-a852-460f-bd61-20d84a8ea42b"}
...
{"component":"virt-handler","controller":"vm","level":"error","msg":"cannot compute checksums as containerdisk/kernelboot containers seem to have been terminated","pos":"vm.go:572","timestamp":"2026-05-19T08:00:26.287317Z"}
...
{"component":"virt-handler","kind":"","level":"info","msg":"Bind mounting container disk at root: /proc/1/root, relative: /run/containerd/io.containerd.runtime.v2.task/k8s.io/12e7a2016270a079b426c1b93da658cbeaa6ff69e22834476543d71aeb478b08/rootfs/disk/customized-image.qcow2 to   
  root: /var/lib/kubelet/pods/5d8ca961-e318-44cf-87a0-42e1eba2c995/volumes/kubernetes.io~empty-dir/container-disks, relative:                                                                                                                                                             
  /disk_0.img","name":"kubevirtvmi-1","namespace":"default","pos":"mount.go:316","timestamp":"2026-05-19T08:00:26.302731Z","uid":"3c8d6d7d-a852-460f-bd61-20d84a8ea42b"}

The checksum fails to be computed since the socket is not ready yet. Once the socket gets ready the chechsum is not retried.

The same for the other two VM pods. Checking with Gemini this seems to be a known issue without any proper fix (unverified).

I wonder why it started happening now. 1.35 works even with the bumped kubevirt version. Maybe the kind image is built differently?

ingvagabund · 2026-05-19T10:09:17Z

Running TestLiveMigrationInBackground over k8s1.35/kv1.6.2 while building the kind image locally (via the newly added kind build node-image) works. 1.36 kind image introduces some delays?

Even with k8s1.35/kv1.8.2 the test passes.

Adds ensureVMIsLiveMigratable in TestLiveMigrationInBackground. After the existing wait for virt-launcher pods to reach Running, poll each VMI for the LiveMigratable=True condition. If a VMI fails to become migratable within 120s, delete and recreate it (up to 3 attempts). This works around an upstream KubeVirt race where virt-handler computes the containerdisk checksum before the disk socket is ready, fails, and never retries. The recreated VMI lands on a node that has already cached the containerdisk image, so the socket comes up before virt-handler's first attempt. The race surfaces consistently with the kind v1.36.1 node image, causing TestLiveMigrationInBackground to fail with "Expected at least 3 finished live migrations, got less: 0".

Reverts b767b9c. The helper was added to work around what looked like the virt-handler containerdisk-socket race on k8s 1.36, but the actual root cause is unrelated: k8s 1.36's stricter CRD numeric format validation (kubernetes/kubernetes#136582) rejects VMI status updates with the pre-fix uint32 Checksum schema. See kubevirt/kubevirt#17858 for the upstream context and kubevirt/kubevirt#17469 for the upstream fix (merged to main, included in v1.9.0-alpha.0, not in v1.8.x). The follow-up commit bumps KUBEVIRT_VERSION so the test consumes a KubeVirt release that contains the fix, which removes the need for any test-side retry.

KubeVirt v1.8.2 publishes VMI status checksum fields (uint32 in Go) as format: int32 in its generated CRD schema. k8s 1.36 enables strict numeric format validation in CRDs via kubernetes/kubernetes#136582, which now rejects the legacy schema and causes virt-handler to enter an infinite VMI status update re-enqueue loop. Live migrations never complete and the descheduler e2e TestLiveMigrationInBackground times out. The schema fix landed upstream in kubevirt/kubevirt#17469 (merged to main on 2026-04-18, included in v1.9.0-alpha.0 tagged 2026-05-11) but was not backported to release-1.8, so no v1.8.x release contains it. Bump the default KUBEVIRT_VERSION to v1.9.0-alpha.0 so the e2e suite consumes a release whose generated CRDs are compatible with k8s 1.36's stricter validator. Tracked in kubevirt/kubevirt#17858.

Copilot

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

ingvagabund · 2026-05-19T19:26:24Z

Looks like it helps to enable ImageVolume feature gate (allowing to skip the checksum computation):

  apiVersion: kubevirt.io/v1                                                                                                                                                                                                                                                              
  kind: KubeVirt                                                                                                                                                                                                                                                                          
  metadata:                                                                                                                                                                                                                                                                               
    name: kubevirt                                                                                                                                                                                                                                                                        
    namespace: kubevirt
  spec:
    configuration:
      developerConfiguration:
        featureGates:
          - ImageVolume

The e2e is passing now locally on top of this PR.

kubectl -n kubevirt patch kubevirt kubevirt --type=merge --patch '{"spec":{"configuration":{"developerConfiguration":{"featureGates":["ImageVolume"]}}}}'

Making another test round just to be sure.

EDIT: yeap, confirmed. Applying the kubectl patch (right after the first one) command makes the test pass (at least locally).

a7i · 2026-05-19T19:51:19Z

Looks like it helps to enable ImageVolume feature gate (allowing to skip the checksum computation):

  apiVersion: kubevirt.io/v1                                                                                                                                                                                                                                                              
  kind: KubeVirt                                                                                                                                                                                                                                                                          
  metadata:                                                                                                                                                                                                                                                                               
    name: kubevirt                                                                                                                                                                                                                                                                        
    namespace: kubevirt
  spec:
    configuration:
      developerConfiguration:
        featureGates:
          - ImageVolume

The e2e is passing now locally on top of this PR.

kubectl -n kubevirt patch kubevirt kubevirt --type=merge --patch '{"spec":{"configuration":{"developerConfiguration":{"featureGates":["ImageVolume"]}}}}'

Making another test round just to be sure.

EDIT: yeap, confirmed. Applying the kubectl patch (right after the first one) command makes the test pass (at least locally).

fyi, I linked the issue where this is fixed in the RC kubevirt/kubevirt#17858

ingvagabund · 2026-05-19T20:00:56Z

Oh, nice. So this is a known issue on the other side as well. Thanks for the detailed report and coordination with the kubevirt folks.

a7i · 2026-05-19T20:12:59Z

Shall we merge this PR then? @ingvagabund

ingvagabund · 2026-05-19T20:18:07Z

/lgtm

ingvagabund · 2026-05-19T20:18:49Z

Let's keep the commits as they are for historical purposes. In case we need to revisit/see the path walked :)

…escheduler (0.35.1 ➔ 0.36.0) (#586) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [ghcr.io/home-operations/charts-mirror/descheduler](https://github.com/kubernetes-sigs/descheduler) | minor | `0.35.1` → `0.36.0` | --- ### Release Notes <details> <summary>kubernetes-sigs/descheduler (ghcr.io/home-operations/charts-mirror/descheduler)</summary> ### [`v0.36.0`](https://github.com/kubernetes-sigs/descheduler/releases/tag/v0.36.0): Descheduler v0.36.0 [Compare Source](kubernetes-sigs/descheduler@v0.35.1...v0.36.0) #### What's Changed - fix(ci): pin helm-unittest plugin version and bump chart-testing-action by [@a7i](https://github.com/a7i) in [#1834](kubernetes-sigs/descheduler#1834) - Update helm RBAC to account for pvc failure on 0.35.0 by [@cayla](https://github.com/cayla) in [#1836](kubernetes-sigs/descheduler#1836) - Add init containers support to Helm chart by [@kamleshjoshi8102](https://github.com/kamleshjoshi8102) in [#1826](kubernetes-sigs/descheduler#1826) - Change icon URL in Chart.yaml by [@a7i](https://github.com/a7i) in [#1838](kubernetes-sigs/descheduler#1838) - fix: resolve detected data races by [@ingvagabund](https://github.com/ingvagabund) in [#1842](kubernetes-sigs/descheduler#1842) - fix(ci): upgrade codeql-action to v4 and clean up security workflow by [@a7i](https://github.com/a7i) in [#1847](kubernetes-sigs/descheduler#1847) - update golang semconv dependencies by [@sammedsingalkar09](https://github.com/sammedsingalkar09) in [#1848](kubernetes-sigs/descheduler#1848) - Extend PodLifeTime with condition, exit code, owner kind, and transition time filters by [@a7i](https://github.com/a7i) in [#1844](kubernetes-sigs/descheduler#1844) - security: Update trivy-action to use sha for v0.35.0 by [@Priyankasaggu11929](https://github.com/Priyankasaggu11929) in [#1854](kubernetes-sigs/descheduler#1854) - security: upgrade grpc and otel sdk dependencies by [@sammedsingalkar09](https://github.com/sammedsingalkar09) in [#1859](kubernetes-sigs/descheduler#1859) - evictions: fix missing observability for background evictions by [@tiraboschi](https://github.com/tiraboschi) in [#1856](kubernetes-sigs/descheduler#1856) - fix(descheduler): reset prometheus usage client at each extension point by [@tiraboschi](https://github.com/tiraboschi) in [#1862](kubernetes-sigs/descheduler#1862) - fix(.github/workflows/manifests.yaml): pin actions to a sha by [@ingvagabund](https://github.com/ingvagabund) in [#1868](kubernetes-sigs/descheduler#1868) - cloudbuild: pin gcb-docker-gcloud image by digest by [@Paramesh324](https://github.com/Paramesh324) in [#1871](kubernetes-sigs/descheduler#1871) - chart: allow overriding ServiceMonitor apiVersion by [@a7i](https://github.com/a7i) in [#1837](kubernetes-sigs/descheduler#1837) - ci: pin GitHub Actions to immutable SHAs by [@a7i](https://github.com/a7i) in [#1875](kubernetes-sigs/descheduler#1875) - evictions: fix assumePod silently dropping success metric on informer race by [@tiraboschi](https://github.com/tiraboschi) in [#1873](kubernetes-sigs/descheduler#1873) - chore(defaultevictor): add MatchExpressions compatibility to the namespaceselector by [@Fankhauserli](https://github.com/Fankhauserli) in [#1853](kubernetes-sigs/descheduler#1853) - fix(test/setupTestSandbox): wait until initial objects are propagated to informers by [@ingvagabund](https://github.com/ingvagabund) in [#1878](kubernetes-sigs/descheduler#1878) - \[v0.36.0] release prep: bump k8s/go deps, manifests, docs, and CI matrix by [@a7i](https://github.com/a7i) in [#1874](kubernetes-sigs/descheduler#1874) #### New Contributors - [@kamleshjoshi8102](https://github.com/kamleshjoshi8102) made their first contribution in [#1826](kubernetes-sigs/descheduler#1826) - [@Priyankasaggu11929](https://github.com/Priyankasaggu11929) made their first contribution in [#1854](kubernetes-sigs/descheduler#1854) - [@Paramesh324](https://github.com/Paramesh324) made their first contribution in [#1871](kubernetes-sigs/descheduler#1871) - [@Fankhauserli](https://github.com/Fankhauserli) made their first contribution in [#1853](kubernetes-sigs/descheduler#1853) **Full Changelog**: <kubernetes-sigs/descheduler@v0.35.0...v0.36.0> </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.erwanleboucher.dev/eleboucher/homelab/pulls/586

…uler ( 0.35.1 ➔ 0.36.0 ) (#85) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [ghcr.io/home-operations/charts-mirror/descheduler](https://github.com/kubernetes-sigs/descheduler) | minor | `0.35.1` → `0.36.0` | --- > ⚠️ **Warning** > > Some dependencies could not be looked up. Check the [Dependency Dashboard](issues/34) for more information. --- ### Release Notes <details> <summary>kubernetes-sigs/descheduler (ghcr.io/home-operations/charts-mirror/descheduler)</summary> ### [`v0.36.0`](https://github.com/kubernetes-sigs/descheduler/releases/tag/v0.36.0): Descheduler v0.36.0 [Compare Source](kubernetes-sigs/descheduler@v0.35.1...v0.36.0) #### What's Changed - fix(ci): pin helm-unittest plugin version and bump chart-testing-action by [@a7i](https://github.com/a7i) in [#1834](kubernetes-sigs/descheduler#1834) - Update helm RBAC to account for pvc failure on 0.35.0 by [@cayla](https://github.com/cayla) in [#1836](kubernetes-sigs/descheduler#1836) - Add init containers support to Helm chart by [@kamleshjoshi8102](https://github.com/kamleshjoshi8102) in [#1826](kubernetes-sigs/descheduler#1826) - Change icon URL in Chart.yaml by [@a7i](https://github.com/a7i) in [#1838](kubernetes-sigs/descheduler#1838) - fix: resolve detected data races by [@ingvagabund](https://github.com/ingvagabund) in [#1842](kubernetes-sigs/descheduler#1842) - fix(ci): upgrade codeql-action to v4 and clean up security workflow by [@a7i](https://github.com/a7i) in [#1847](kubernetes-sigs/descheduler#1847) - update golang semconv dependencies by [@sammedsingalkar09](https://github.com/sammedsingalkar09) in [#1848](kubernetes-sigs/descheduler#1848) - Extend PodLifeTime with condition, exit code, owner kind, and transition time filters by [@a7i](https://github.com/a7i) in [#1844](kubernetes-sigs/descheduler#1844) - security: Update trivy-action to use sha for v0.35.0 by [@Priyankasaggu11929](https://github.com/Priyankasaggu11929) in [#1854](kubernetes-sigs/descheduler#1854) - security: upgrade grpc and otel sdk dependencies by [@sammedsingalkar09](https://github.com/sammedsingalkar09) in [#1859](kubernetes-sigs/descheduler#1859) - evictions: fix missing observability for background evictions by [@tiraboschi](https://github.com/tiraboschi) in [#1856](kubernetes-sigs/descheduler#1856) - fix(descheduler): reset prometheus usage client at each extension point by [@tiraboschi](https://github.com/tiraboschi) in [#1862](kubernetes-sigs/descheduler#1862) - fix(.github/workflows/manifests.yaml): pin actions to a sha by [@ingvagabund](https://github.com/ingvagabund) in [#1868](kubernetes-sigs/descheduler#1868) - cloudbuild: pin gcb-docker-gcloud image by digest by [@Paramesh324](https://github.com/Paramesh324) in [#1871](kubernetes-sigs/descheduler#1871) - chart: allow overriding ServiceMonitor apiVersion by [@a7i](https://github.com/a7i) in [#1837](kubernetes-sigs/descheduler#1837) - ci: pin GitHub Actions to immutable SHAs by [@a7i](https://github.com/a7i) in [#1875](kubernetes-sigs/descheduler#1875) - evictions: fix assumePod silently dropping success metric on informer race by [@tiraboschi](https://github.com/tiraboschi) in [#1873](kubernetes-sigs/descheduler#1873) - chore(defaultevictor): add MatchExpressions compatibility to the namespaceselector by [@Fankhauserli](https://github.com/Fankhauserli) in [#1853](kubernetes-sigs/descheduler#1853) - fix(test/setupTestSandbox): wait until initial objects are propagated to informers by [@ingvagabund](https://github.com/ingvagabund) in [#1878](kubernetes-sigs/descheduler#1878) - \[v0.36.0] release prep: bump k8s/go deps, manifests, docs, and CI matrix by [@a7i](https://github.com/a7i) in [#1874](kubernetes-sigs/descheduler#1874) #### New Contributors - [@kamleshjoshi8102](https://github.com/kamleshjoshi8102) made their first contribution in [#1826](kubernetes-sigs/descheduler#1826) - [@Priyankasaggu11929](https://github.com/Priyankasaggu11929) made their first contribution in [#1854](kubernetes-sigs/descheduler#1854) - [@Paramesh324](https://github.com/Paramesh324) made their first contribution in [#1871](kubernetes-sigs/descheduler#1871) - [@Fankhauserli](https://github.com/Fankhauserli) made their first contribution in [#1853](kubernetes-sigs/descheduler#1853) **Full Changelog**: <kubernetes-sigs/descheduler@v0.35.0...v0.36.0> </details> --- ### Configuration 📅 **Schedule**: (in timezone America/New_York) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.greyrock.io/greyrock-labs/home-ops/pulls/85

Copilot AI review requested due to automatic review settings May 16, 2026 02:18

Copilot AI reviewed May 16, 2026

View reviewed changes

k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels May 16, 2026

k8s-ci-robot requested review from googs1025 and knelasevero May 16, 2026 02:18

a7i force-pushed the descheduler-v0.36.0 branch from 1020379 to 4b309fe Compare May 16, 2026 18:56

Copilot AI review requested due to automatic review settings May 17, 2026 01:39

a7i force-pushed the descheduler-v0.36.0 branch from 4b309fe to b1686ea Compare May 17, 2026 01:39

Copilot AI reviewed May 17, 2026

View reviewed changes

Copilot AI review requested due to automatic review settings May 17, 2026 01:55

Copilot AI reviewed May 17, 2026

View reviewed changes

a7i force-pushed the descheduler-v0.36.0 branch 2 times, most recently from be07fd4 to c5caedb Compare May 17, 2026 02:05

Copilot AI review requested due to automatic review settings May 17, 2026 02:05

Copilot AI reviewed May 17, 2026

View reviewed changes

a7i force-pushed the descheduler-v0.36.0 branch from aef6ccc to e860517 Compare May 17, 2026 14:14

Copilot AI review requested due to automatic review settings May 17, 2026 14:14

Copilot AI reviewed May 17, 2026

View reviewed changes

a7i force-pushed the descheduler-v0.36.0 branch from e860517 to d4f3c20 Compare May 17, 2026 14:17

Copilot AI review requested due to automatic review settings May 17, 2026 14:22

a7i force-pushed the descheduler-v0.36.0 branch from d4f3c20 to 09af9a0 Compare May 17, 2026 14:22

Copilot AI reviewed May 17, 2026

View reviewed changes

a7i force-pushed the descheduler-v0.36.0 branch from 09af9a0 to aae77a8 Compare May 17, 2026 14:23

k8s-ci-robot requested review from ingvagabund and jklaw90 May 17, 2026 19:02

k8s-ci-robot assigned jklaw90 May 17, 2026

a7i added 3 commits May 18, 2026 12:15

[v0.36.0] release prep: bump k8s/go deps, manifests, docs, and CI matrix

3f8f9bb

ci(manifests): build kind node image for k8s v1.36.1

0883de7

test(e2e): harden kind install and align lint tooling

dfc3166

a7i force-pushed the descheduler-v0.36.0 branch from 89e3199 to dfc3166 Compare May 18, 2026 16:15

k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 18, 2026

Copilot AI review requested due to automatic review settings May 19, 2026 02:40

Copilot AI reviewed May 19, 2026

View reviewed changes

a7i mentioned this pull request May 19, 2026

VMI status update loop on k8s 1.36: ContainerDiskInfo/KernelInfo/InitrdInfo Checksum (uint32) hit strict CRD format validation kubevirt/kubevirt#17858

Open

a7i added 2 commits May 19, 2026 15:05

Copilot AI review requested due to automatic review settings May 19, 2026 19:06

Copilot AI reviewed May 19, 2026

View reviewed changes

k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 19, 2026

k8s-ci-robot merged commit 8005cdf into kubernetes-sigs:master May 19, 2026
9 checks passed

anshulg-dep-review Bot mentioned this pull request May 21, 2026

Update Helm release descheduler to v0.36.0 ansg191-lab/anshulg-cluster#3239

Open

1 task

Conversation

a7i commented May 16, 2026

What changed

Why

Validation

Suggested reviewer focus

Release impact

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

a7i commented May 17, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

a7i commented May 17, 2026

Uh oh!

jklaw90 commented May 17, 2026

Uh oh!

ingvagabund commented May 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

a7i commented May 18, 2026

Uh oh!

ingvagabund commented May 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

ingvagabund commented May 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ingvagabund commented May 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

ingvagabund commented May 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

a7i commented May 19, 2026

Uh oh!

ingvagabund commented May 19, 2026

Uh oh!

a7i commented May 19, 2026

Uh oh!

ingvagabund commented May 19, 2026

Uh oh!

ingvagabund commented May 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

ingvagabund commented May 18, 2026 •

edited

Loading

ingvagabund commented May 18, 2026 •

edited

Loading

ingvagabund commented May 19, 2026 •

edited

Loading

ingvagabund commented May 19, 2026 •

edited

Loading

ingvagabund commented May 19, 2026 •

edited

Loading

ingvagabund commented May 19, 2026 •

edited

Loading